Liquid filling and dispensing method

ABSTRACT

A liquid filling and dispensing method comprises determining whether a user account is valid; if the user account is valid: enabling a user to obtain operating parameters of a processing assembly configured to collect and transfer liquid to a filling assembly; enabling the user to find a fill location having the filling assembly, wherein the fill assembly is configured to fill a validated container with liquid; and enabling the user to initiate filling of the container with the liquid at the filling assembly.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation-in-part of, and claims priority toand the benefit of, U.S. patent application Ser. No. 17/651,658, filedFeb. 18, 2022; which is a continuation-in-part of U.S. patentapplication Ser. No. 17/451,131, filed Oct. 15, 2021; which is acontinuation-in-part of U.S. patent application Ser. No. 17/380,178,filed Jul. 20, 2021; which is a continuation-in-part of U.S. patentapplication Ser. No. 17/176,350, filed Feb. 16, 2021, all of which areincorporated herein in their entirety.

BACKGROUND OF THE DISCLOSURE

The present disclosure generally relates to liquid systems and, moreparticularly, to methods of filling and dispensing liquid in acontainer.

Consumers often avoid drinking water from the tap. Accordingly,consumers frequently purchase pre-filled bottles of water. The bottlesare often made of plastic and discarded after a single use. Thatcontributes to environmental waste which does not quickly degrade. Also,the consumer must travel to a store to purchase more plastic bottles ofwater.

When the consumer is in a rented space, such as a hotel room or evenvehicle, bottled water is often provided for a charge. However, theowner of the space may need to constantly replenish the bottles of waterand discard the used bottles. At the same time, the owner may need totrack the number of consumed bottles of water and charge the consumeraccordingly.

As can be seen, there is a need for improved methods to fill anddispense liquid.

SUMMARY OF THE DISCLOSURE

In one aspect of the present disclosure, a liquid filling and dispensingmethod comprises determining whether a user account is valid; if theuser account is valid: enabling a user to obtain operating parameters ofa processing assembly configured to collect and transfer liquid to afilling assembly; enabling the user to find a fill location having thefilling assembly, wherein the fill assembly is configured to fill avalidated container with liquid; and enabling the user to initiatefilling of the container with the liquid at the filling assembly.

In another aspect of the present disclosure, a non-transitorycomputer-readable storage medium storing instructions which, whenexecuted by a computer processor, cause the computer processor toperform a liquid filling and dispensing method, and comprises enabling auser to find a fill location having a filling assembly, wherein the fillassembly is configured to fill a container with liquid; and enabling theuser to initiate filling of the container, from a bottom area thereof,with the liquid at the filling assembly.

In a further aspect of the present disclosure, a computer implementedmethod for liquid filling and dispensing comprises enabling a validateduser to select a user action among: finding a fill location having afilling assembly, wherein the fill assembly is configured to fill avalidated container with liquid; and initiating the filling of thecontainer, from a bottom area thereof, with the liquid at the fillingassembly.

These and other features, aspects and advantages of the presentdisclosure will become better understood with reference to the followingdrawings, description, and claims.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a schematic diagram of a liquid filling and dispensing systemaccording to an exemplary embodiment of the present disclosure.

FIG. 2 is a schematic diagram of a processing assembly according to anexemplary embodiment of the present disclosure.

FIG. 3 is a schematic diagram of a filling assembly according to anexemplary embodiment of the present disclosure.

FIG. 4A is an exploded view of a filling assembly according to anexemplary embodiment of the present disclosure.

FIGS. 4B-4C are cross sectional views of a filling assembly according toan exemplary embodiment of the present disclosure.

FIGS. 5A-5B are flow charts depicting a mobile application according toan exemplary embodiment of the present disclosure.

FIGS. 6A-6I are databases according to an exemplary embodiment of thepresent disclosure.

FIGS. 7A-7B are flow charts of a filling process according to anexemplary embodiment of the present disclosure.

FIGS. 8A-8B are flow charts of a monetization process according to anexemplary embodiment of the present disclosure.

FIG. 9 is a flow chart of a user account setup process according to anexemplary embodiment of the present disclosure.

DETAILED DESCRIPTION OF THE DISCLOSURE

The following detailed description is of the best currently contemplatedmodes of carrying out the disclosure. The description is not to be takenin a limiting sense, but it is merely for the purpose of illustratingthe general principles of the disclosure, since the scope of thedisclosure is best defined by the appended claims.

Various inventive features are described below that can each be usedindependently of one another or in combination with other features.However, any single inventive feature may not address any of theproblems discussed above or may only address one of the problemsdiscussed above. Further, one or more of the problems discussed abovemay not be fully addressed by any of the features described below.

As used herein, the terms “embodiment” and “embodiments” are intended tobe used interchangeably. In other words, the singular includes theplural, and vice versa.

As will be appreciated by one skilled in the art, aspects of the presentdisclosure may be embodied as a system, method, or computer programproduct. Accordingly, aspects of the present disclosure may take theform of an entirely hardware embodiment, an entirely software embodiment(including firmware, resident software, micro-code, etc.) or anembodiment combining software and hardware aspects that may allgenerally be referred to herein as a “circuit,” “module,” “assembly,” or“system”. Furthermore, aspects of the present disclosure may take theform of a computer program product embodied in one or more computerreadable media having computer readable program code embodied thereon.

Any combination of one or more non-transitory computer readable storagemedia may be utilized. A non-transitory computer readable storage mediumis an electronic, magnetic, optical, or semiconductor system, apparatus,or device, or any suitable combination of the foregoing. More specificexamples (a non-exhaustive list) of the computer readable storage mediumwould include the following: a portable computer diskette, a hard disk,a random-access memory (RAM), a read-only memory (ROM), an erasableprogrammable read-only memory (EPROM or Flash memory), a portablecompact disc read-only memory (CD-ROM), an optical storage device, amagnetic storage device, or any suitable combination of the foregoing.In the context of this document, a computer readable storage medium isany tangible medium that can store a program for use by or in connectionwith an instruction execution system, apparatus, or device.

A non-transitory computer readable signal medium may include apropagated data signal with computer readable program code embodiedtherein, for example, in baseband or as part of a carrier wave. Such apropagated signal may take any of a variety of forms, including, but notlimited to, electro-magnetic, optical, or any suitable combinationthereof. A computer readable signal medium may be any computer readablemedium that is not a computer readable storage medium and that cancommunicate, propagate, or transport a program for use by or inconnection with an instruction execution system, apparatus, or device.

Program code embodied on a non-transitory computer readable medium maybe transmitted using any appropriate medium, including but not limitedto wireless, wireline, optical fiber cable, RF, etc., or any suitablecombination of the foregoing.

Computer program code for carrying out operations for aspects of thepresent disclosure may be written in any combination of one or moreprogramming languages, including an object-oriented programming languagesuch as Java, Smalltalk, C++ or the like and conventional proceduralprogramming languages, such as the “C” programming language or similarprogramming languages. The program code may execute entirely on theuser's computer, partly on the user's computer, as a stand-alonesoftware package, partly on the user's computer and partly on a remotecomputer or entirely on the remote computer or server. In the latterscenario, the remote computer may be connected to the user's computerthrough any type of network, including a local area network (LAN) or awide area network (WAN), or the connection may be made to an externalcomputer (for example, through the Internet using an Internet ServiceProvider).

Aspects of the present disclosure are described below with reference toflowchart illustrations and/or block diagrams of methods, apparatus(systems) and computer program products according to embodiments of thedisclosure. It will be understood that each block of the flowchartillustrations and/or block diagrams, and combinations of blocks in theflowchart illustrations and/or block diagrams, can be implemented bycomputer program instructions. These computer program instructions maybe provided to a processor of a general purpose computer, specialpurpose computer, or other programmable data processing apparatus toproduce a machine, such that the instructions, which execute via theprocessor of the computer or other programmable data processingapparatus, create means for implementing the functions/acts specified inthe flowchart and/or block diagram block or blocks.

These computer program instructions may also be stored in anon-transitory computer readable storage medium that can direct acomputer, other programmable data processing apparatus, or other devicesto function in a particular manner, such that the instructions stored inthe computer readable storage medium produce an article of manufactureincluding instructions which implement the function/act specified in theflowchart and/or block diagram block or blocks.

The computer program instructions may also be loaded onto a computer,other programmable data processing apparatus, or other devices to causea series of operational steps to be performed on the computer, otherprogrammable apparatus or other devices to produce a computerimplemented process such that the instructions which execute on thecomputer or other programmable apparatus provide processes forimplementing the functions/acts specified in the flowchart and/or blockdiagram block or blocks.

Here, the technical problems to be solved are that environmental wasteis created from plastic containers having liquids for human consumption.In various vendor-consumer environments, the provision of liquid inplastic containers needs to enable only paying consumers to obtaincontainers of liquid.

Broadly, the present disclosure solves the foregoing problems byproviding apparatus and methods for filling and dispensing liquid, suchas water, for human consumption. In the present disclosure, liquid maybe stored and then pumped to a filling assembly. The present disclosuremay enable the easy and quick attachment/detachment of a container(e.g., bottle) to a filling assembly, whereby the container can befilled with liquid and then removed for liquid consumption. Inembodiments, the container can be reusable. The present disclosure maydetermine—via a verification subassembly—whether the container is valid.If valid, and based on stored characteristics of the container, thepresent disclosure may fill the container with liquid. The presentdisclosure may enable a user to have an account which can be monetarilycharged each time a container is filled.

FIG. 1 is a schematic diagram of an exemplary embodiment of a liquidfilling and dispensing system 10. In exemplary embodiments, the system10 may be in a vehicle, in a hotel room, in a restaurant, or in otherenvironments such as where the controlled dispensing of liquid into acontainer is desired.

In an embodiment, the system 10 may include a processing assembly 11which operatively communicates with a filling assembly 13 and with acomputer 12 (i.e., a CPU/processor/controller/database). In anembodiment, the computer 12 may be separate from the processing assembly11 and separate from the filling assembly 13. Or, in an embodiment, thecomputer 12 may be a part of the processing assembly 11 or a part of thefilling assembly 13. In an embodiment, the computer 12 may storeinformation in a cloud 14, or locally.

According to an embodiment, a user device 15—such as a desktop, alaptop, mobile phone, or computer—may communicate with the system10—wirelessly or wired. For example, the user device 15 may initiate astart of the processing assembly 11, initiate a start of the fillingassembly 13, and/or initiate a creation of a user account as furtherdescribed below.

In an embodiment, the processing assembly 11 may provide a processing ofliquid that can be transported to the filling assembly 13. Inembodiments, the liquid may be water. In other embodiments, the liquidmay be a drink suitable for human consumption, such as juice, soda orcoffee.

The processing assembly 11 may, in an embodiment, be configured to storeand pump a liquid among tanks and filters. In an embodiment, theprocessing assembly 11 may be further configured to pump the liquid tothe filling assembly 13. The filling assembly 13 may determine whether acontainer is valid or not. If valid, according to an embodiment, thefilling assembly 13 may then use stored characteristics of the containerto fill the container with liquid, such as water.

FIG. 2 is a schematic diagram of an exemplary embodiment of theprocessing assembly 11. The processing assembly 11 may, in anembodiment, collect liquid in a collection tank 21. From the collectiontank 21, a pump 22 may pump the liquid through a filter 23 to removeparticulates and/or contaminants, for example. The filtered liquid fromthe filter 23 may move into a clean tank 24, according to an embodiment.A pump 25 may then pump the filtered liquid from the clean tank 24 andthrough a valve 26 to produce a consumable liquid 29, in an embodiment.From the valve 26, the consumable liquid 29 may be transferred to thefilling assembly 13.

The processing assembly 11 may, in embodiments, include a power supply27 that may supply power to one or more of the components in theassembly 11, such as the pumps 22, 25. In embodiments, the processingassembly 11 may also include a computer 28 (i.e.,CPU/processor/controller/database) to communicate with and control theoperation of one or more of the components in the assembly 11. Inanother embodiment, the computer 12 may communicate with and control theoperation of one or more of the components in the assembly 11. In anembodiment, the computers 12, 28 may store information in the cloud 14,or locally.

In embodiments, the computer/controller 12, 28 may be configured todetermine whether the collection tank 21 is empty (e.g., via a sensor inthe tank 21) and/or to start/stop operation of one or more of thecomponents in the processing assembly 11.

In an embodiment where the liquid is water, the processing assembly 11may acquire humidified air from an environment outside of the system 10,such as the air inside and/or outside of a vehicle. The processingassembly 11 may be further configured to condense water from thehumidified air (i.e., dehumidify the humidified air). According to anembodiment, the processing assembly 11 may also be configured to filterthe humidified air and/or filter the condensed water. The foregoing isfurther described in U.S. patent application Ser. No. 17/451,131, filedOct. 15, 2021, which is incorporated herein in its entirety.

FIG. 3 is a schematic diagram of an exemplary embodiment of the fillingassembly 13. In embodiments, the filling assembly 13 may have averification subassembly which may include an RFID reader 35 that mayread an RFID tag on a container 34 to be filled with liquid. A statusLED 37 may indicate the filling status of the assembly 13. The fillingassembly 13 may further include a weighing subassembly which may includea load cell 39 that may weigh a container 34 that is empty or full ofliquid or partially full of liquid. A UV-LED 40 may be included in thefilling assembly 13, in an embodiment, and which can destroy bacteriaand the like before liquid enters the container 34. In an embodiment, avalve 41 may receive liquid 29 from the processing assembly 11 and aliquid line 42 may direct the liquid into the container 34.

In the filling assembly 13, according to an embodiment, a computer 36(i.e., CPU/processor/controller/database) may communicate with andcontrol one or more of the other components in the filling assembly 13.In another embodiment, the computer 12 may communicate with and controlone or more of the components in the filling assembly 13. In anembodiment, the computers 12, 36 may store information in the cloud 14,or locally.

FIG. 4A is a partial, exploded view of a filling assembly 13, accordingto an exemplary embodiment. The filling assembly 13 may include a basesubassembly 13 a, a connection subassembly 13 b, a verificationsubassembly 13 c, a weighing subassembly 13 d, and a cover 44 to housethe foregoing subassemblies, in an embodiment.

According to an embodiment, the cover 44 may have an aperture 44 atherein, wherein the aperture 44 a can be positioned operativelyadjacent to and receive the container 34 to be filled with liquid,according to an embodiment. The cover 44 may include a lid 44 b, in anembodiment, which may include a planar element 44 c which can rotateabout a post element 44 d. In an embodiment, the filling assembly 13(e.g., the base subassembly 13 a) may move the lid 44 b over theaperture 44 a when the filling assembly 13 is not in use and may movethe lid 44 b to expose the aperture 44 a when the filling assembly 13 isin use.

In an embodiment, one or more UV-LEDs 40 can be supported by the cover44. One or more of the UV-LEDs 40 may be disposed at a side of theplanar element 44 c which interfaces the aperture 44 a, according to anembodiment. As noted above, the one or more UV-LEDs may destroy bacteriaand the like before liquid enters the container 34.

In FIG. 4, according to an embodiment, the base subassembly 13 a can beconfigured to receive liquid from the processing assembly 11. In anembodiment, the base subassembly 13 a may include a container holder 45which can be configured to receive and hold the container 34, such as ata bottom area thereof. In an embodiment, the container holder 45 can becup shaped. In an embodiment, the container holder 45 may include one ormore receiving slots or elements 45 a which, for example, may bepositioned about an exterior cylindrical surface of the container holder45. One or more of the receiving slots 45 a may be configured to receiveat least a part of the connection subassembly 13 b as described below.

The base subassembly 13 a may include a liquid line 42 that maytransport liquid from the processing assembly 11 to the base subassembly13 a, according to an embodiment. In an embodiment, the liquid line 42may extend into the container holder 45, such as through a bottom areaof the container holder 45 and eventually attach to the connectionsubassembly 13 b, as described below.

In an embodiment, the base subassembly 13 a may include a base plate 49.The base plate 49, in an embodiment, may have a planar bottom element 49a at a bottom thereof, a cup shaped element 49 b affixed on the bottomelement 49 a, and one or more post elements 49 c affixed on the bottomelement 49 a and which may be disposed near and/or along a perimeter ofthe bottom element 49 a. The cup shaped element 49 b may be configuredto receive and hold the container holder 45, in an embodiment. The oneor more post elements 49 c may support the cover 44 over the base plate49, in an embodiment.

In FIG. 4A, the base subassembly 13 a, such as the bottom element 49 aof the base plate 49, may support thereon at least a portion of theconnection subassembly 13 b, according to an embodiment. In anembodiment, the base subassembly 13 a may be configured to enable theconnection subassembly 13 b to move in a direction parallel to alongitudinal axis 34 d of the container 34 (FIG. 4B).

In an embodiment, the bottom element 49 a of the base plate 49 maysupport one or more solenoids 50 in an upright orientation and whichsolenoids 50 form a part of the connection subassembly 13 b. In anembodiment, the one or more solenoids 50 may be positioned outside ofand about the cup shaped element 49 b of the base plate 49. In anembodiment, the one or more solenoids 50 may operatively interface theone or more slots 45 a on the container holder 45.

In an embodiment, the base subassembly 13 a may include a base connector52. The base connector 52 may, in an embodiment, connect to and enableliquid communication between the connection subassembly 13 b and theliquid line 42.

In FIG. 4A, according to an embodiment, the base subassembly 13 a, suchas the bottom element 49 a of the base plate 49, may support thereon atleast a portion of the weighing subassembly 13 d. In an embodiment, theweighing subassembly 13 d may include a load cell 39 and an interfaceboard 53 to control the former. In an embodiment, the load cell 39 maybe positioned within the cup shaped element 49 b of the base plate 49,while the interface board 53 may be positioned outside of the cup shapedelement 49 b.

In an embodiment, the base subassembly 13 a, such as the cup shapedelement 49 b of the base plate 49, may support thereon at least aportion of the verification subassembly 13 c. The verificationsubassembly 13 c may include the RFID reader 35.

In an embodiment, the base subassembly 13 a may include the computer 36described above. The base subassembly 13 a may further include amotor/gearbox 54 which can rotate the cover lid 44 b over and away fromthe cover aperture 44 a. In an embodiment, as described below, when thefill assembly 13 is in a fill position/state, the motor/gearbox 54 maybe initiated, via the computer 36, to move the cover lid 44 b away fromthe cover aperture 44 a. In an embodiment, when the fill assembly 13 isin a non-fill position/state, the motor/gearbox 54 may be initiated, viathe computer 36, to move the cover lid 44 b over from the cover aperture44 a.

In FIG. 4A, the connection subassembly 13 b may include a first coupling51, in an embodiment. The first coupling 51 may be a female couplingthat can be configured to releasable mate/connect with a second coupling(e.g., male coupling) of the connection subassembly 13 b, though notshown in FIG. 4A.

In FIG. 4B, a cross section of the filling assembly 13 is shown. Thefilling assembly 13 may include a container 34 configured to receiveliquid from the base subassembly 13 a. In an embodiment, the container34 can have a body portion 34 g, a cap 34 a configured to fit at one end(i.e., top area) of the body portion 34 g and enable consumption ofliquid therein, and a bottom portion or area 34 b at an opposite end(i.e., top area) of the body portion 34 g. In an embodiment, the bottomarea 34 b may be configured to provide a receiving portion or void space34 c on an exterior of the container 34. According to an embodiment, thecontainer 34 may extend along the longitudinal axis 34 d. The container34 may further include an RFID tag 34 e, such as on an exterior surfaceof the bottom area 34 b of the container 34. The RFID tag 34 e may, inan embodiment, contain information about the container 34 and/or a user.

As shown in FIG. 4B, the container 34 may be placed in a fillposition/state, such as by the user. In an embodiment, the user mayinsert the container 34, such as the bottom area 34 b thereof, into thecontainer holder 45. A force of gravity on the container 34 may occur asthe user releases the container 34 into the container holder 45. Theforce of gravity may be parallel to the longitudinal axis 34 d,depending on the orientation of the filling assembly 13. Herein, theterm “parallel” is intended to mean “exactly parallel”, as well as“generally parallel” or “substantially parallel.”

Also, in an embodiment, an applied force may be created on the container34 in the fill position/state. The applied force may be external to thefilling assembly 13 and result from the user pushing down on thecontainer 34 towards the container holder 45, according to anembodiment. The externally applied force can be parallel to thelongitudinal axis 34 d of the container 34, according to an embodiment.

The connection subassembly 13 b can be activated, according to anembodiment, as or upon the container 34 being placed in the fillposition. The connection subassembly 13 b may be configured toreleasably connect/mate the container 34 with the base subassembly 13 a,in an embodiment. The connection subassembly 13 b may also be configuredto releasably connect/mate, as above, by an applied force(s) that is(are) perpendicular or parallel to the longitudinal axis 34 d of thecontainer 34, in an embodiment. Herein, the term “perpendicular” isintended to mean “exactly perpendicular”, as well as “generallyperpendicular” or “substantially perpendicular”.

Accordingly, in an embodiment, the connection subassembly 13 b may beconfigured to releasably connect/mate, as above, by two forces that areorthogonal to one another. The connection subassembly 13 b may beconfigured to transport liquid in only one direction therein—from thebase subassembly 13 a to the container 34—in an embodiment. Theconnection subassembly 13 b may also be configured to create a liquidpressure differential therein.

In FIGS. 4A-4B, according to an embodiment, the connection subassembly13 b may include a microswitch holder 58 which, for example, may bedonut shaped. The microswitch holder 58 may support one or moremicroswitches 55, in an embodiment. The microswitch holder 58 and themicroswitch(es) 55 may be disposed in the container holder 45, in anembodiment.

The one or more microswitches 55 may be configured and disposed to sensethe presence of the container 34, in an embodiment. For example, the oneor more of the microswitches 55 may be positioned in the containerholder 45. When the bottom area 34 b of the container 34 contacts one ormore of the microswitches 55, the one or more microswitches 55 may senda signal to the computer 36 indicating the presence of the container 34,in an embodiment. The computer 36 may, in turn, then activate othercomponents of the fill assembly 13, such as the one or more solenoids50. In an embodiment, the computer 36 may, in turn, be configured toactivate one or more of the components in the processing assembly 11.

Similarly, according to an embodiment, the one or more microswitches 55may be configured to sense the absence of the container 34. In such asituation, the one or more microswitches 55 may not send a signal to thecomputer 36. The computer 36 may, in turn, be configured to prevent theactivation of one or more of the components in the fill assembly 13and/or the processing assembly 11.

In FIG. 4B, according to embodiments, the connection subassembly 13 bcan include a first coupling 51 and a second coupling 56. The first andsecond couplings 51, 56 may be configured to couple and decouple by afriction fit, according to an embodiment. The first and second couplings51, 56 may, in embodiments, be male and female couplings. In anembodiment, the first coupling 51 may be a female coupling and thesecond coupling 56 may be a male coupling.

An embodiment of a first and second coupling 51, 56 herein is furtherdescribed in U.S. patent application Ser. No. 17/451,131, filed Oct. 15,2021, which is incorporated herein in its entirety.

Referring still to FIG. 4B, in an embodiment, the first coupling 51 maybe attached to either the container 34 or the base subassembly 13 a,while the second coupling 56 may be attached to the other of thecontainer 34 and the base assembly 13 a. In the fill position/state,according to an embodiment, when the first and second couplings 51, 56can be releasably connected to one another, the couplings 51, 56 maycreate a liquid pressure differential therein, according to anembodiment. The pressure differential may result from pressurized liquidentering one of the couplings (e.g., the first coupling 51) andpressurized liquid exiting the other of the couplings (e.g., the secondcoupling 56) and into the container 34, according to an embodiment. Inembodiments, pressure of the liquid entering the coupling 51 can behigher than the pressure of the liquid exiting the coupling 56. In anembodiment, the higher pressure of the liquid entering the coupling 56may be due to the liquid being pumped from the processing assembly 11.In an embodiment, the lower pressure of the liquid exiting the coupling56 may be due to a low liquid pressure in the container 34.

The connection subassembly 13 b can be disconnected or inactivated,according to an embodiment, as or upon the container 34 being removedfrom the fill position to the non-fill position wherein liquid is notentering the container 34. In an embodiment, as the user removes thecontainer 34 from the stationary container holder 45, the first andsecond couplings 51, 56 may decouple. In an embodiment, the decouplingmay occur due to the loss of friction fit between the first coupling 51and the second coupling 56.

Upon decoupling, liquid can be prevented from passing from one couplingto another, such as from the first coupling 51 to the second coupling56, in an embodiment. Also, upon decoupling, the coupling 51 or 56attached to the container 34 is configured to prevent liquid fromexiting the container 34 through such coupling.

In FIGS. 1 and 4A, the verification subassembly 13 c can include theRFID reader 35 adjacent the container holder 45 and the RFID tag 34 e onthe container 34, according to an embodiment. When the container 34 isoperatively near or in the container holder 45, the reader 35 may readthe tag 34 e, in an embodiment. When read, the computer 36 may determinewhether the container 34 is valid or not. In other words, determinewhether the user has a valid user account and/or whether the container34 is an authorized (i.e., valid) container to be filled with liquid.

In FIG. 4C, a partial cross section of the filling assembly 13 is shown.In an embodiment, the container holder 45 may include a bottom portionor area 45 b and an upstanding wall 45 c extending perpendiculartherefrom. One or more apertures 45 d may be in the wall 45 c, accordingto an embodiment.

The connection subassembly 13 b may be configured to impart an appliedforce that can be perpendicular to the longitudinal axis 34 d of thecontainer 34, according to an embodiment. The applied force can be fromthe one or more solenoids 50, in an embodiment. Each solenoid 50 caninclude a post element 50 a arranged lengthwise in a direction parallelto the longitudinal axis 34 d. An attachment element 50 b may besupported at one end of the post element 50 a, in an embodiment. Theattachment element 50 b may, in turn, support an insertion element 50 c.

In an embodiment, the insertion element 50 c may be configured to beinserted into a receiving slot 45 a on the upstanding wall 45 c of thecontainer holder 45. Further, the insertion element 50 c may beconfigured with a recessed surface that interfaces the upstanding wall45 c to produce a gap between the insertion element 50 c and theupstanding wall 45 c.

In FIG. 4C, the connection subassembly 13 b may include one or more ballbearings 50 e and one or more races, according to an embodiment. In anembodiment, the ball bearing(s) 50 e and the race(s) can be configuredto interface the container 34 with the base assembly 13 a. Each ballbearing 50 e can be configured to fit in a respective aperture in theupstanding wall 45 c. In an embodiment, the ball bearing 50 e can befurther configured to fit in the race. The race, in an embodiment, canbe on an exterior surface of the container 34 and, in an embodiment,extend about a circumference of the container 34.

According to an embodiment, in the non-fill position before thecontainer 34 is moved into the container holder 45, the ball bearing(s)50 e may remain in the aperture(s) of the upstanding wall 45 c. At oraround that time, the insertion element(s) 50 c can be positionedwhereby the recessed surface thereon leaves the gap at the position ofthe ball bearing 50 e, in an embodiment. Thereby, there is little or noapplied pressure on the ball bearing 50 e in a direction perpendicularto the longitudinal axis 34 d of the container 34.

In an embodiment, when the container 34 is moved into or near thecontainer holder 45 to the fill position, the RFID reader 35 may readRFID tag 34 e and thereby sense the presence of the container.Alternatively, or in addition, the one or more microswitches 55 may bedepressed and sense the presence of the container 34. The RFID reader 35and/or the one or more microswitches 55 may then signal the computer 36to activate the one or more solenoid(s) 50, in an embodiment. Uponactivation, the insertion element 50 c may move to a position toeliminate the gap, according to an embodiment. By such gap elimination,the insertion element 50 c can impart an applied force on the ballbearing 50 e, in an embodiment. The applied force can be perpendicularto the longitudinal axis 34 d of the container 34. In an embodiment, theapplied force can move the ball bearing 50 e into and/or against therace. That can enable the container 34 to be held in the containerholder 45.

In FIGS. 4B-4C, the weighing subassembly 13 d may include a load cell 39in communication with a ball bearing 57, in an embodiment. The ballbearing 57 may be in continuous contact with the bottom 45 b of thecontainer holder 45—whether the container 34 is in the fill or non-fillposition—according to an embodiment. Thus, when the container 34 is inthe fill position in the container holder 45, the weight of thecontainer 34 is transferred to the ball bearing 57 and then to the loadcell 39, in an embodiment. The load cell 39 can read the weight of thecontainer 34—before, during and after filling—and send the informationto the computer 36.

In turn, the computer 36 may be configured to determine whether thecontainer 34 is to be filled (completely or partially) or not, in anembodiment. The computer may be configured to determine whether theprocessing assembly 11 is to be activated or not, in an embodiment.

According to an embodiment, the computers 12 and/or 36 (i.e., thecontrollers) may be configured to identify a presence of the container34 operatively adjacent to the filling assembly 13 (such as by readingRFID sensor 35 when the user moves the container 34 over or near thefilling assembly 13), determine whether the RFID tag 34 e on thecontainer 34 is valid (such as by checking a database of valid RFIDtags), and if the RFID tag is valid, activate a flow of liquid from theprocessing assembly 11 and/or the filling assembly 13 and into thecontainer 34.

In an embodiment, the controllers 12 and/or 36 may be further configuredto obtain physical characteristics of the container 34 (such as bychecking a database of physical characteristics of containers havingvalid RFID tags), display instructions on a user device 15, initiate areading of a weight of the container 34, determine whether a weight ofthe container 34 is in a valid weight range (such as by checking adatabase of valid weight ranges of valid containers), and determinewhether the container 34 is full of liquid (such as by checking adatabase of weights of full containers).

In an embodiment, data relating to container identity, containerphysical characteristics, and container weight range may be stored inthe database 12, in the cloud 14, or locally. In an embodiment, identitydata may be data that relates a specific (i.e., valid) container 34 to avalid (i.e., authorized) user account. In an embodiment, physicalcharacteristic data may relate to a type of the container, a size of thecontainer, a volume capacity of the container, and/or an empty weightand/or a filled weight of a valid container associated with a valid useraccount. In an embodiment, weight range date may be data of a range ofweights for a valid container—empty and filled.

In the foregoing embodiment, the controllers 12 and/or 36 may be furtherconfigured to identify a presence of the container 34 operativelyadjacent to the filling assembly 13, determine whether an RFID tag 34 eis valid, cause a load cell 39 to measure a weight of the container 34,compare the weight of the container with a valid weight range, andactivate the processing assembly 11 and/or a valve 41 in the fillingassembly 13.

In a further embodiment, the controllers 12 and/or 36 may be configuredto determine whether an RFID tag 34 e on a container 34 at the fillingassembly 13 is valid, determine if there is a valid user accountassociated with the RFID tag, enable a valid user to purchase a fill ofliquid, and activate the processing assembly 11 and/or initiate thefilling assembly 13 to fill liquid into the container 34.

In the foregoing embodiment, the controllers 12 and/or 36 may be furtherconfigured to determine whether the system 10 is available to dispenseliquid, identify a presence of the container 34 at the filling assembly13, enable an invalid user to set up an account, process a purchaseagainst an account of the valid user, disable the container 34 in anaccount of the valid user, and provide a receipt of the purchase to thevalid user.

FIGS. 5A-5B are flow charts of a method 300 of filling and dispensing aliquid according to an exemplary embodiment of the present disclosure.In an embodiment, the method 300 may be a computer implemented method.In an embodiment, the method 300 may be a non-transitorycomputer-readable storage medium storing instructions which, whenexecuted by a computer processor, cause a computer processor to performthe liquid filling and dispensing method. In an embodiment, the method300 may be a mobile device application (“mobile app”) which may be runon a mobile phone, for example.

In an embodiment, the method 300 may start at 301, such as a home pageof a mobile app. At 302, a user may indicate whether the user has anaccount for the mobile app. If “no”, then at 201, the user may start toset up an account according to a method 200 (FIG. 9). If “yes”, then at303, the user may enter log in information, such as name, email, andpassword. At 304, the method 300 may determine whether the log ininformation is for a valid user account based on information in acloud-based database 12. In an embodiment, an Account table 401, a Usertable 402, and a Pass table 403 of the database 12 (FIGS. 6A, 6B, and 6Cfurther described below) can be used to validate the log in information.

At 304, if “no”, then return to 303. If “yes”, then proceed to 305 toreset a password or to 306 to wirelessly connect, such as by Bluetooth,to the processing assembly 11.

At 306, if there is a failed connection, then at 307, an error messagemay be displayed and enable the user to retry connecting. If there is asuccessful connection, then at 308, the user may be enabled to obtainoperating parameters of the processing assembly 11. For example,operating parameters may include temperature, humidity, filter status,and tank levels. In an embodiment, an Account table 401 of the database12 (FIG. 6A further described below) can be used to obtain the operatinginformation which may receive sensor information from sensor(s) in theprocessing assembly.

Thereafter, at 309, the user may proceed to 310 at which the user mayadjust settings, such as on/off, location sharing, user profile, andprivacy information. One or more of the foregoing settings may be storedin the database 12.

At 309, the user may proceed to 311 at which the user may request help,such as through a third-party customer service program, like Zendesk™.

From 309, the user may select among a plurality of user actions. Inembodiments, the user actions may include, at 312, obtaining informationabout the amount of liquid previously consumed from the container. Theuser actions may include, at 313, initiating the filling of liquid intothe container. The user actions may include, at 314, shopping for andpurchasing items related to the processing assembly 11, the fillingassembly 13, and/or the container 34. The user actions may include, at315, finding a fill location (i.e., a geographical location) having thefilling assembly 13.

If 312 is selected, then at 316, the information obtained may be sent tothe cloud storage 14 or a third party. If to be sent to a third party,then at 317, the information may be sent via a third-party applicationprogramming interface. In an embodiment, a Consume table 407 of thedatabase 12 (FIG. 6G further described below) can be used to access theinformation to be sent.

If 313 is selected, the method 300 can proceed to 51 whereby the usercan initiate a method 50 of filling the container 34 with the liquid atthe filling assembly 13 (FIGS. 7A-7B further described below). In anembodiment, the filling assembly 13 can be located at a private onlyaccessible fill location. In other words, the fill location can be at anon-public location, such as the user's vehicle that the public does notgenerally access.

If 314 is selected, the method 300 can proceed to 318 where the user canbe enabled to shop at an e-commerce website.

If 315 is selected, the method 300 can enable the user to geographicallyfind a fill location where a filling assembly 13 is located. In anembodiment, the filling assembly 13 can be located at a publiclyaccessible fill location. In other words, the fill location can be at apublic location, such as a hotel or restaurant. At 315, the user mayfind a fill location by accessing the Account table 401 and aFill_Location table 409 of the database 12 (FIGS. 6A and 6I furtherdescribed below).

From 315, the method 300 can proceed to 81 that can enable a user toproceed through a monetization method 80 (FIGS. 8A-8B further describedbelow). In an embodiment, the method 80 can include the filling method50.

As mentioned above, in an embodiment, the database 12 can include aplurality of tables. As shown in FIGS. 6A-6I, the tables may includeAccount table 401, User table 402, Pass table 403, CCard table 404,Trans_Log table 405, Bottle table 406, Consume table 407, Health table408, and Fill_Location table 409.

In FIG. 6A, according to an embodiment, the Account table 401 mayconsolidate data from the other tables in the database 12. The Accounttable 401 may have columns for a “key” that can include data thatrepresents a unique user. The Account table may have, as examples, rowsfor “userID”, “passID”, “cardID”, “bottleID” “awgID”, “awgStatus”, and“healthID”. The userID may include user name data of the unique user.The passID may include password data of the unique user. The cardID mayinclude credit card data of the unique user. The bottleID may includephysical characteristic data of the container of the unique user. TheawgID may include processing assembly 11 data associated with the uniqueuser. The health ID may include liquid consumption data for thecontainer of the unique user.

In FIG. 6B, according to an embodiment, the User table 402 may havecolumns for the “key” in the Account table 401. The User table may have,as examples, rows for the “userID” in the Account table 401,“firstname”, “lastname”, “addr1”, “addr2”, “city”, “state”, “zip”,“phone”, “email”, the “passID” in the Account table 401, “date_created”,and “status”. The foregoing going rows may include data of the uniqueuser. For example, the “status” may include data about recent activityto show if account is valid, disabled or flagged for possible fraud, etcof the unique user.

In FIG. 6C, according to an embodiment, the Pass table 403 may havecolumns for the “key” in the Account table 401. The Pass table may have,as examples, rows for the “passID” in the Account table 401, “status”,“pass_id”, “last_activity-date”, and “expire_date”. The foregoing goingrows may include data of the unique user. For example, the “status” mayinclude data about recent activity to show if account is valid,disabled, flagged due to suspicious activity, etc of the unique user.The “pass_id” may include data about corresponding record containing theencrypted password for the account of the unique user.

In FIG. 6D, according to an embodiment, the CCard table 404 may havecolumns for the “key” in the Account table 401. The CCard table mayhave, as examples, rows for the “userID” in the Account table 401,“status”, “token_id”, “card_id” in the Account table 401, “card_type”,“last_activity_date”, and “expire_date”. The foregoing going rows mayinclude data of the unique user. For example, the “status” may includedata about recent activity to show if account is valid, disabled,flagged due to suspicious activity, etc. of the unique user. Forexample, the “token_id” may include data about unique informationmatching stored values to use for future credit card processing withoutdisclosing actual credit card information of the unique user.

In FIG. 6E, according to an embodiment, the Transaction_Log table 405may have columns for the “key” in the Account table 401. TheTransaction_Log table may have, as examples, rows for the “userID” inthe Account table 401, “card_id” in the Account table 401,“location_id”, and “transaction_type”. The foregoing going rows mayinclude data of the unique user. For example, the “location_id” mayinclude data about referencing the specific location record store in the“Fill_LocationsDB” of the unique user. For example, the“transaction_type” may include data about the type of service associatedwith the transaction for example refill bottle, purchase new bottle,refund, etc of the unique user.

In FIG. 6F, according to an embodiment, the Bottle table 406 may havecolumns for the “key” in the Account table 401. The Bottle table mayhave, as examples, rows for the “userID” in the Account table 401,“rfid_code”, “bottle_type”, “fill_cap”, and “status”. The foregoinggoing rows may include data of the unique user. For example, the“rfid_code” may include data about a unique identification number storedwith the RFID chip found on the bottom of the bottle of the unique user.For example, the “bottle_type” may include data about specificcharacteristics of the bottle including revision of bottle design, valuedesigns, etc of the unique user. For example, the “fill_cap” may includedata about how much liquid (calaculated based on volume of water) thebottle can store of the unique user. For example, the “status” mayinclude data about recent activity to show if account is valid, disabledor flagged as missing, stolen, etc of the unique user.

In FIG. 6G, according to an embodiment, the Consume table 407 may havecolumns for the “key” in the Account table 401. The Consume table mayhave, as examples, rows for the “userID” in the Account table 401,“transdate”, and “consume”. The foregoing going rows may include data ofthe unique user. For example, the “consume” may include data about howmuch liquid was previously consumed from the container of the uniqueuser.

In FIG. 6H, according to an embodiment, the Health table 408 may havecolumns for the “key” in the Account table 401. The Health table mayhave, as examples, rows for the “userID” in the Account table 401,“transdate”, “consumeID”, “healthID” in the Account table 401,“healthName”, and “url”. The foregoing going rows may include data ofthe unique user. For example, the “consumeID” may include data aboutwhich record is associated with this user from the ConsumeDB of theunique user. For example, the “healthID” may include data about theIdentification number used by third party accounts and system thatcorrespond to the unique user. For example, the “health Name” mayinclude data about third party service associated with the of the uniqueuser. For example, the “url” may include data about website address forthe third-party service provider for their health storage system of theunique user.

In FIG. 6I, according to an embodiment, the Fill_Locations table 409 mayhave columns for the “key” in the Account table 401. The Fill_Locationstable may have, as examples, rows for the “locnID”, “locnname”,“locn_displayname”, “ownerID” in the Account table 401, “addr1”,“addr2”, “city”, “state”, “zip”, “status”, “locn_lat”, and “locn_long”.The foregoing going rows may include data of publicly accessible filllocations having a fill assembly. For example, the “locnID” may includedata about referencing the specific location record store in the“Fill_LocationsDB” of the unique fill location. For example, the“locnname” may include data about a unque identification text referenceof the unique fill location. For example, the “ownerID” may include dataabout the individual that owns the Fill Station that is located at thatlocation of the unique fill location. For example, the “status” mayinclude data about ability to provide filling capabilities, recentactivity to show location is valid, disabled, etc of the unique filllocation.

As mentioned above, the method 300 may include the filling method 50.Accordingly, the method 50 may be a computer implemented method. In anembodiment, the method 50 may be a non-transitory computer-readablestorage medium storing instructions which, when executed by a computerprocessor, cause a computer processor to perform the filling method. Inan embodiment, the method 50 may be a mobile device application (“mobileapp”) which may be run on a mobile phone, for example.

FIGS. 7A-7B are flowcharts that depict the filling method 50 accordingto an embodiment.

At block 51, the system 10 can be powered on (such as by a power switchin the processing assembly 11). At block 52, determine whether thecollection tank 21 is empty (such as by a sensor in the tank 21). Ifyes, then at block 55, display a “no liquid available” message on theuser device 15. If no, then at block 53, wait for a container 34 to beoperatively adjacent to the filling assembly 13.

At block 54, detect and read an RFID tag 34 e on the container 34. Ifnone detected, return to block 53. If detected, then at block 57,determine whether the RFID tag is valid (such as from the Account table401 and the Bottle table 406 of the database 12). If not valid, at block56, display an “invalid” message on the user device. If valid, at block58, obtain physical characteristics of the container 34 (e.g., correctweight range)(such as from the Account table 401 and the Bottle table406).

Following block 58, at block 59, display “place container in holder”message on the user device. At block 60, the load cell 39 measures theweight of the container 34. At block 61, compare measured weight againstvalid weight ranges. If not valid, then return to block 59. If valid, atblock 62, start countdown to start of filling liquid. At block 63,activate the pump 25, the valve 26, the solenoid(s) 50, and the UV-LED40. At block 64, liquid is flowing from the processing assembly 11 andinto the filling assembly 13.

At block 65, the load cell 39 measures the weight of the container 34.At block 66, determine whether the container 34 is full of water bycomparing an empty weight to a full weight (such as from the Accounttable 401 and the Bottle table 406). If yes, then at block 67, stop thepump 25, close the valve 26, disable the solenoid (s) 50, and turn offthe UV-LED 40. At block 68, display “fill complete” message on the userdevice, and then return to the start 51. If not full, then at block 69,determine whether the container 34 has been removed from the fillingassembly 13 (such as by a sudden change in the reading from the loadcell 39).

In an embodiment, a “sudden change” may be as follows. The load cell 39may continually monitor the weight of the container 34 during thefilling process. As the filling process is somewhat linear, the expectedweight change can be determined and monitored while filling. The weightreadings can occur about 30-35 times a second. If, during the fillingprocess, there is a different result, the controller 12 and/or 36 cannote a “bad” reading, starting a process that will check for up to twomore bad readings in succession. If this occurs, the controller 12and/or 36 can assume that something has gone wrong and can stop thefilling process by closing the valve 26 and switching off the pump 25.If the bad readings do not reach the three-result threshold, thecontroller 12 and/or 36 can reset and continue as normal.

If the container 34 has not been removed, then return to block 65, Ifyes, then stop pump 25, close the valve 26, disable the solenoid(s) 50,and turn off the UV-LED 40. Next, at block 71, display “error” messageon the user device, and return to block 59.

As mentioned above, the method 300 may include the monetization method80. Accordingly, the method 80 may be a computer implemented method. Inan embodiment, the method 80 may be a non-transitory computer-readablestorage medium storing instructions which, when executed by a computerprocessor, cause a computer processor to perform the filling method. Inan embodiment, the method 80 may be a mobile device application (“mobileapp”) which may be run on a mobile phone, for example.

FIGS. 8A-8B are flowcharts that depict the monetization method 80according to an embodiment.

At block 81, the system 10 can be powered on (such as by a power switchin the processing assembly 11). At block 82, determine whether thesystem 10 is available to dispense liquid to third persons (such as byreading the setting in the database 12 of the users the owner wishes toallow liquid to be available). If no, then at block 83, display a “noliquid available” message on the user device. If yes, then at block 84,wait for a container 34 to be operatively adjacent to the fillingassembly 13.

At block 85, detect and read an RFID tag 34 e on the container 34. Ifnone detected, return to block 84. If detected, then at block 86,determine whether the RFID tag is valid (such as from the Account table401 and the Fill_Location table 6I of the database 12). If not valid, atblock 87, display an “invalid” message on the user device. If valid, atblock 89, obtain user information (such as from the Account table 401and the Fill_Location table 6I of the database 12).

At block 89, determine whether the user has a valid user account (suchas from the Account table 401 and the Fill_Location table 6I of thedatabase 12). If no valid user account, at block 90, display message“set up account?” on the user device. If no, at block 91, displaymessage “account needed” on the user device. If yes, at block 92,display screen to start set up process with user device 15.

At block 89, if yes to having a valid user account, then at block 94,display message “welcome” on the user device. Then at block 95, displaymessage “ready to fill bottle” on the user device. At block 96, displaymessage “proceed to purchase?” on the user device. If no, then at block97, display message “cancel/goodbye” on the user device, and the processreturns to block 81. If yes, then at block 98, the bottle fillingprocess starts (such as that described in process 50).

At block 99, display message of total cost of purchase on the userdevice. At block 100, process the purchase against the valid useraccount. At block 101, run payment processor action. At block 102,determine if purchase is successful. If no, at block 103, disablecontainer in user account and then at block 104, display message “error”on the user device.

If purchase is successful, at block 105, display message “want areceipt” on the user device. If no, at block 106, display message“goodbye” on the user device and return to block 81. If yes, at block107, email receipt of purchase to user

In embodiments, blocks 99 through 107 may be implemented by any suitablee-commerce program that enables a user to purchase a product/serviceonline.

At block 108, close out transaction in any suitable accounting systemthat can remote from the system 10, and then continue to blocks 106 and81.

As mentioned above, the method 300 may include the set up account method200. Accordingly, the method 200 may be a computer implemented method.In an embodiment, the method 200 may be a non-transitorycomputer-readable storage medium storing instructions which, whenexecuted by a computer processor, cause a computer processor to performthe filling method. In an embodiment, the method 200 may be a mobiledevice application (“mobile app”) which may be run on a mobile phone,for example.

FIG. 9 is a flowchart that depicts the set-up account method 200according to an embodiment.

In an embodiment, at block 201, the method may start. At block 202, theuser device 15 decodes a QR code from the processing assembly 11 to getan RFID number. (If the user does not have a QR code, the user canmanually populate a form.) At block 203, display a form on the userdevice 15 to capture user information. At block 204, user entersinformation. At block 205, determine if user email already exists in thedatabase 12. If yes, at block 206, display error message and return toblock 203. If no, create unique account in the database 12 (such as inthe Account table 401, the User table 402, and the Transaction_Log 405).

At block 207, add RFID number from above to account. At block 208,display a form on the user device to capture credit card information(which can be stored in the CCard table 404). At block 209, verifycredit card information with payment processor. At block 210, creditcard processor uses credit card stripe. At block 211, is credit cardgood? If no, at block 212, display error message and then return toblock 208. If yes, at block 213, store credit card token in the CCardtable 404. At block 214, display message that setup is complete and, atblock 215, end process, such as by continuing in the monetizationprocess 80. In an embodiment, the process 200 may continue at block 94of the monetization process 80.

It should be understood, of course, that the foregoing relates toexemplary embodiments of the disclosure and that modifications may bemade without departing from the spirit and scope of the disclosure asset forth in the following claims.

We claim:
 1. A liquid filling and dispensing method, comprising:determining whether a user account is valid; if the user account isvalid: enabling a user to obtain operating parameters of a processingassembly configured to collect and transfer liquid to a fillingassembly; enabling the user to find a fill location having the fillingassembly, wherein the fill assembly is configured to fill a validatedcontainer with liquid; and enabling the user to initiate filling of thecontainer with the liquid at the filling assembly.
 2. The method ofclaim 1, further comprising: enabling the user to determine an amount ofliquid previously consumed from the container.
 3. The method of claim 1,further comprising: enabling the user to purchase items associated withthe processing assembly, the filling assembly, and the container.
 4. Themethod of claim 1, further comprising: determining whether an RFID tagon the container is valid.
 5. The method of claim 1, further comprising:comparing data on an RFID tag that is on the container to a databasehaving data of valid containers.
 6. The method of claim 1, furthercomprising: obtaining physical characteristics of the container.
 7. Themethod of claim 1, further comprising: determining whether a weight ofthe container is in a valid weight range.
 8. A non-transitorycomputer-readable storage medium storing instructions which, whenexecuted by a computer processor, cause the computer processor toperform a liquid filling and dispensing method, comprising: enabling auser to find a fill location having a filling assembly, wherein the fillassembly is configured to fill a container with liquid; and enabling theuser to initiate filling of the container, from a bottom area thereof,with the liquid at the filling assembly.
 9. The method of claim 8,wherein: the fill location is at least one of a publicly accessible filllocation and a private only accessible fill location.
 10. The method ofclaim 8, wherein the bottom area of the container is opposite a top areaof the container from which the user can consume the liquid.
 11. Themethod of claim 8, further comprising: determining whether a user has anaccount that is valid.
 12. The method of claim 8, further comprising:determining whether information on the container is valid before fillingthe container with the liquid.
 13. The method of claim 8, furthercomprising: determining a weight of the container before and during thefilling of the container with the liquid.
 14. A computer implementedmethod for liquid filling and dispensing, comprising: enabling avalidated user to select a user action among: finding a fill locationhaving a filling assembly, wherein the fill assembly is configured tofill a validated container with liquid; and initiating the filling ofthe container, from a bottom area thereof, with the liquid at thefilling assembly.
 15. The method of claim 14, wherein the user actionfurther comprises: enabling the user to determine an amount of liquidpreviously consumed from the container.
 16. The method of claim 14,wherein the user action further comprises: enabling the user to purchaseitems associated with the processing assembly, the filling assembly, andthe container.
 17. The method of claim 14, further comprising:determining whether a user has an account that is valid.
 18. The methodof claim 14, further comprising: comparing data on an RFID tag that ison the container to a database having data of valid containers.
 19. Themethod of claim 14, further comprising: determining a weight of thecontainer before and during the filling of the container with theliquid.
 20. The method of claim 14, further comprising: obtainingphysical characteristics of the container.